-
Notifications
You must be signed in to change notification settings - Fork 79
Clarify backup/restore strategy regarding system db #2521
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
Clarify backup/restore strategy regarding system db #2521
Conversation
a2314dc
to
c670af6
Compare
This option ensures that the backup includes not only `users` and `roles`, but also the cluster topology. | ||
Cluster topology metadata, stored in the `system` database, defines the servers in the cluster and their operational modes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This part is incorrect. Backing up a user database never backs up the topology, and it would be annoying if it did. 'all' does in fact just mean both 'users' and 'roles'.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the guidance about including metadata is in fact no different between clustered and standalone - if you want to backup your RBAC, include the metadata.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, it looks like I misunderstood the card.
We can create a dump of the system
database, but it won't help us to retain the cluster topology.
a8d7711
to
e1e30f3
Compare
This PR includes documentation updates Updated pages: |
No description provided.